Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1588

reference
289-tree-1
name
1588
tree-preservation-order

undefined

289-tpo-1
uprn
address-text
point
POINT (-1.040556 50.897696)
geometry
MULTIPOLYGON (((-1.040514 50.897692,-1.040515 50.897700,-1.040521 50.897708,-1.040531 50.897714,-1.040543 50.897718,-1.040556 50.897719,-1.040569 50.897718,-1.040581 50.897714,-1.040590 50.897708,-1.040597 50.897701,-1.040599 50.897692,-1.040597 50.897684,-1.040591 50.897677,-1.040582 50.897671,-1.040570 50.897667,-1.040557 50.897665,-1.040544 50.897666,-1.040532 50.897670,-1.040522 50.897676,-1.040516 50.897683,-1.040514 50.897692)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL